big problems with abit kt7a-raid ewsxl and w2k

[gomf]

hi all!
until now the stress control panel has helped me very much solving all my problems with the ews :-) thankx!
but now i don't get it going under w2k...
i cannot get rid of these yellow excalmation marks on digital control and sythesizer. another thing is a device called
%*CSCA8AA.DeviceDesc% that has never been there before in win9x... i've also tried changing biossettings like pnpos enabled/disabled and stuff...

can somebody help me??

[jerry janson]

I had the same shit under winme, terratec is not giving any support for winme but has drivers for win2k like u use. Sorry but i had to turn back too to win98se that works best. i use 1000mhz amd thunderbird on kt7a-abit with win98se, works perfect. Why always want the newest? if it works it works.

[gomf]

well i just got an email from terratec and they said i should try to all the pnp settings to "real" adresses in the eeprom of my card, then it should work.. i will try this tomorrow *jawn* i hope this'll work... i really like w2k much more than w98 (more stabile *g*)

[gomf]

it didn't work... somebody else any ideas??

[rash]

Hi!

I have also tried to get the EWS64XL to run in Win2000. First of all the problems with the device called %*CSCA8AA.DeviceDesc% is due to a wrong driver installation procedure (your fault). Remove the devices from the control panel, restart and reinstall the drivers.

But the bigger problem is, the IRQ allocation. The solution from Terratec is the only way it works. For changing the "hard settings" use the ews64neu.exe DOS application with a modified ews64neu.ini file (self-explanatory).

But changing to Win2000 is a more difficult problem. I hope your ABIT board is running stable and you have installed all the Servicepacks and Patches. The VIA chipset of the board makes a lot of troubles with USB, Firewire and IRQ assignment. Have a look at Paul's Unofficial ABIT KT7 Motherboard FAQ (http://www.viahardware.com/faq/kt7/kt7faq.htm) if you did not before.

I hope Terratec will develop a more stable driver for win2000, because the current 1.8 drivers do not work together with all software and do not have DirectX support. For example my video editing software AIST MovieDVSuite does fucks up when the drivers are installed.

rash

[rash]

remark: I use a ABIT KT7A-Board

[gomf]

Hi!

First: thanks for the good tipps! BUT:
I tried to get rid of that %*CSCA8AA.DeviceDesc% thing. So I did as you said and after rebooting w2k installed this "device" again...

then: what is that about with this terratec solution? what should i change in this ews64neu.ini?

I now have installed all the latest drivers, patches and so on...
and thanks for that forum-link! :-)

but I slowly start being disappointed using my ews... under win98 it only runs when i have disabled my lpt... this also is no real good solution..

unhappy,

GoMf!

[Arnoud de Jong]

Guys, guys... When do you finally face the hard truth: Win2k has NOT been designed for multimedia purposes. It's an 'office' platform. So don't waste your precious time on trying to get it fully working with your EWS. If you want the best of both worlds, make a dual boot system with Win98se and W2k. The codec should work under W2k, but for the rest: use Win98. And who knows: maybe the upcoming Windows XP will do a better job here

[gomf]

okay! that is what i am doing right now: win98 and w2k parallel, BUT how can i run the codec on w2k when it should be disabled in win98...
i'm sorry that i don't know how to solve this but right now nothing works under w2k and when i want to for example go listening to new vinyl in the internet i have to start 98 cause w2k has NO sound!?

[philippz]

Hi Arnoud,

Windows 2000 is very useable for multimedia purposes, but the EWS 64 is not useable with Windows 2000...

All major sequencer programs(Cubase, Cakewalk Sonar, Logic with upcoming 5.0) are switching to the Win2K platform. With the new WDM driver model, Win 2k will be superior to Win 98 SE in music purposes. Besides that, it doesn?t crash half as often.
In fact, my Windows 2000 system I?m just using to write this didn?t crash anymore since I deactivated the EWS 64 drivers.

There?s just one problem: to properly use Windows 2000, the hardware companies will have to write GOOD! WDM drivers. Maybe there will be one for the EWS 64 in 2005 or so...

That?s the real reason to stay with Win 98.

Bye, Philipp